Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(aws-lambda): add null handling for multiValueHeaders #13533

Merged
merged 3 commits into from
Sep 5, 2024

Conversation

windmgc
Copy link
Member

@windmgc windmgc commented Aug 21, 2024

Summary

A small PR for adding a null handling code for the multiValueHeaders field. Also contains a small refactor to put isBase64Encode check into the validate function to keep consistency with other fields

Checklist

  • The Pull Request has tests
  • A changelog file has been created under changelog/unreleased/kong or skip-changelog label added on PR if changelog is unnecessary. README.md
  • There is a user-facing docs PR against https://github.com/Kong/docs.konghq.com - PUT DOCS PR HERE

Issue reference

FTI-6168

@github-actions github-actions bot added plugins/aws-lambda cherry-pick kong-ee schedule this PR for cherry-picking to kong/kong-ee labels Aug 21, 2024
@windmgc windmgc merged commit 50c57c8 into master Sep 5, 2024
26 checks passed
@windmgc windmgc deleted the lambda-json-null-handling branch September 5, 2024 07:28
@team-gateway-bot
Copy link
Collaborator

Successfully created cherry-pick PR for master:

andrewgkew pushed a commit to andrewgkew/kong that referenced this pull request Sep 5, 2024
A small PR for adding a null handling code for the multiValueHeaders field. Also contains a small refactor to put isBase64Encode check into the validate function to keep consistency with other fields

FTI-6168
curiositycasualty pushed a commit that referenced this pull request Oct 15, 2024
A small PR for adding a null handling code for the multiValueHeaders field. Also contains a small refactor to put isBase64Encode check into the validate function to keep consistency with other fields

FTI-6168

(cherry picked from commit 50c57c8)
github-actions bot pushed a commit that referenced this pull request Oct 28, 2024
A small PR for adding a null handling code for the multiValueHeaders field. Also contains a small refactor to put isBase64Encode check into the validate function to keep consistency with other fields

FTI-6168

(cherry picked from commit 50c57c8)
@team-gateway-bot
Copy link
Collaborator

Successfully created backport PR for release/3.8.x:

@team-gateway-bot
Copy link
Collaborator

Cherry-pick failed for master, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally.

git remote add upstream https://github.com/kong/kong-ee
git fetch upstream master
git worktree add -d .worktree/cherry-pick-13533-to-master-to-upstream upstream/master
cd .worktree/cherry-pick-13533-to-master-to-upstream
git checkout -b cherry-pick-13533-to-master-to-upstream
ancref=$(git merge-base c1bd5c6adb9a0d422204cd2e3812bfb54cc4d0cb 8259e8d99e5c54e84f3078bec44e8c73d687cc4c)
git cherry-pick -x $ancref..8259e8d99e5c54e84f3078bec44e8c73d687cc4c

@github-actions github-actions bot added the incomplete-cherry-pick A cherry-pick was incomplete and needs manual intervention label Oct 28, 2024
@kikito kikito removed the incomplete-cherry-pick A cherry-pick was incomplete and needs manual intervention label Oct 29, 2024
windmgc added a commit that referenced this pull request Oct 31, 2024
A small PR for adding a null handling code for the multiValueHeaders field. Also contains a small refactor to put isBase64Encode check into the validate function to keep consistency with other fields

FTI-6168

(cherry picked from commit 50c57c8)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport release/3.8.x cherry-pick kong-ee schedule this PR for cherry-picking to kong/kong-ee plugins/aws-lambda size/M
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants